Add generic navigation apis to Page Navigation - #22010
Conversation
|
You can test this PR using the following package version. |
|
You can test this PR using the following package version. |
| { | ||
| var instance = new T(); | ||
|
|
||
| return PushModalAsyncPrivate(instance, transition); |
There was a problem hiding this comment.
Could we pass null as the third argument here? This currently selects the parameter overload, so the transition becomes Parameter and never runs. PushModalAsyncPrivate(instance, transition, null) could gfix it.
|
You can test this PR using the following package version. |
|
You can test this PR using the following package version. |
|
See this issue for the requested API changes. |
|
You can test this PR using the following package version. |
| /// <summary> | ||
| /// Pushes <paramref name="page"/> onto the navigation stack asynchronously using <see cref="PageTransition"/>, with optional <paramref name="parameter"/>. | ||
| /// </summary> | ||
| public Task PushAsync(Page page, IPageTransition? transition, object? parameter = null) => PushAsyncPrivate(page, transition, parameter); |
There was a problem hiding this comment.
The optional parameter conflicts with the overload right above: make it non-optional.
Applicable to PushAsync, ReplaceAsync and PushModalAsync.
|
You can test this PR using the following package version. |
What does the pull request do?
Implements #21984
Adds new api to
INavigation, allowing custom navigation services to use page navigation without creatingPageinstances.What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues